Date: Sun, 10 May 2009 10:05:45 -0700 From: perryh@pluto.rain.com To: onemda@gmail.com Cc: freebsd-questions@freebsd.org Subject: Re: how to fix "interrupt storm" Message-ID: <4a070969.mYZsiV8emLhJVvVg%perryh@pluto.rain.com> In-Reply-To: <3a142e750905100452s73aa391bjcdc8fea49636ee37@mail.gmail.com> References: <4a04702a.ZaIfHAUzw/YexVK2%perryh@pluto.rain.com> <3a142e750905090746g5324d8ffl1ea10645c0e5f45c@mail.gmail.com> <4a05f963.OI3CMfJ3/j2hbi4D%perryh@pluto.rain.com> <3a142e750905100452s73aa391bjcdc8fea49636ee37@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Paul B. Mahol" <onemda@gmail.com> wrote: > On 5/9/09, perryh@pluto.rain.com <perryh@pluto.rain.com> wrote: > > "Paul B. Mahol" <onemda@gmail.com> wrote: > >> On 5/8/09, perryh@pluto.rain.com <perryh@pluto.rain.com> wrote: > >> > What, exactly, is an "interrupt storm", and how do I fix it? > > ... > >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> > ad6: FAILURE - SET_MULTI status=51<READY,DSC,ERROR> error=4<ABORTED> > >> > ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936 > >> > > >> > etc. etc. until I killed it with ^C. (Just entering "q", to cause > >> > more(1) to exit and presumably stop od(1) with a SIGPIPE, did not > >> > stop the spew of messages.) > >> > > >> > What does this indicate? Hardware problems? Bad configuration? > >> > Something else? > >> > >> Output of "vmstat -i"? > > > > $ vmstat -i > > interrupt total rate > > irq0: clk 497386851 1004 > > irq1: atkbd0 2491 0 > > irq3: xl0 2030 0 > > irq6: fdc0 11 0 > > irq7: ppbus0 ppc0 1 0 > > irq8: rtc 63654324 128 > > irq9: uhci0+ 166216 0 > > uhci0 is doing strange things, what usb device are connected? There are no USB devices connected. I think those must actually be atapci1 interrupts, since irq9 is where dmesg reported it. > It could be bad configuration, bug or hardware problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4a070969.mYZsiV8emLhJVvVg%perryh>